
Andrev Nox
SOMER Blink Cognitive Development
|
Posted - 2011.05.10 05:38:00 -
[1]
The issue:
Over the years, the corp role system has become increasingly antiquated.
At it's inception, it was designed around fairly resource-poor corporations with 10-50 members and 1-3 offices. Even at that time, the roles were a bit too sweeping, but we've always made it work.
In modern day even, when corporations and alliances can have a dozen offices and hundreds of billions in assets, it is far, far too wide a scope.
Currently, there are certain roles which are carte blanche.
Contracts: Allowing someone to make one contract on behalf of the corporation means they can delete any outstanding corporate contracts
Delivery Hangars: Unlike corp hangars, there is no per-station control. Access to one means access to all.
Science/Industry Jobs: Like delivery hangar, there is no location restriction. If someone wants to build some ammo for the corp, you have to trust them not to cancel the titan build 57 jumps away that they didn't even know about.
Wallet Journal: Currently, to allow someone access to view the wallet journal, you also have to allow access to delivery hangars. Equally, granting any type of view role means showing the current contents of all wallet divisions.
Corp Hangars: The current system is based on 3 choices. "Headquarters" "Based at" and "Everything else in the entire universe" - need to give someone POS hangar access? You also have to give them access to every hangar everywhere that isn't the HQ or their based at location.
POS access in general: Giving any type of access to one pos means the same type of access to every pos.
The fixes:
Granularity.
Contracts - "Can Create" and "Can Modify" roles. "Modify" can even be broken down to "Created from Wallet Div X" - but even without that change, just a "Can Modify" flag would eliminate 90% of the problem.
Delivery Hangars - at the least, enable the same flags as currently in place for offices. Ideally, the flags as suggested below for office role reform.
Science and Industry - the same as contracts. Can Install, Can Cancel. Cancel can be broken down to "Installed from location X" for further granularity.
Wallet Journal: The same as hangar roles. "View" and "Take" roles, per division.
Corp Hangars: There is no issue with assigning a contract or market order to a specific station. Why limit hangar roles in the same way? Allow roles to be set on a per-station basis. Ideally, the above Science and Industry roles would fall into this as well.
POS access: If not possible to assign roles through the corp interface for a specific POS, then at least make it possible from the POS equipment itself. An "Allowed" list, rather than an access role.
Overall, these seem to be fairly low-hanging fruit from an outsiders perspective. Yet any one of them alone would represent a massive change in the ability for larger scaled operations to function in a more decentralized way.
Roles, as they stand now, remove the ability for any significant asset usage delegation, as the trust must be nearly-all or none. It provides no opportunity for newer players to work their way upward in their corporate responsibilities in regards to corporate assets. With these changes, the importance of trust in Eve is no less important - but the ability to place a more finely tuned value on that trust becomes far more possible.
Role Reform
|

Andrev Nox
SOMER Blink Cognitive Development
|
Posted - 2011.05.10 20:36:00 -
[2]
Originally by: Planetary Genocide +1.
Being able to have station-based roles for things like Security Officer and whatnot would be really cool but slightly unncessary, but I agree that for things like hangar access it'd be nice to not have to rely on basing someone somewhere and limiting them to one station because of it, or giving them carte blanche access to everything that isn't the HQ
Agreed, some roles would usually be set universally instead of per-station. But that would be the beauty of a "All" or "Specific Station" flag - the ability to choose. :)
Role Reform
|